How is a DXL attribute stored when a baseline is struck? I have some DXL attributes that summarise information from linked modules. When a baseline is struck are the values of the DXL attributes stored (and therefore unchanged when the old baselines are viewed) or is it the DXL that is stored and recalculated when the old baseline is opened (and therefore could change)?
srocca - Thu May 02 03:35:09 EDT 2013 |
Re: Baselines and DXL Attributes In baselines DXL attributes work as they would work in current module versions - the DXL code is executed and the value of DXL attribute is not fixed. If you want to store the value of DXL attribute you have to copy the value to a real attribute before creating a baseline. |
Re: Baselines and DXL Attributes Pekka_Makinen - Thu May 02 05:03:37 EDT 2013 In baselines DXL attributes work as they would work in current module versions - the DXL code is executed and the value of DXL attribute is not fixed. If you want to store the value of DXL attribute you have to copy the value to a real attribute before creating a baseline. Pekka Thank you. I had real trouble finding any information on this and you solved it in a matter minutes. Scott |
Re: Baselines and DXL Attributes srocca - Thu May 02 06:25:47 EDT 2013 Pekka Thank you. I had real trouble finding any information on this and you solved it in a matter minutes. Scott If your DXL attribute is displaying information from linked objects AND both the current module AND the linked module(s) are baselined together in a baseline set, then the DXL attributes will work as expected in the baseline. |